Conversation
mac-kan
force-pushed
the
MBP-330-Brake-With-Diagnostic-Function
branch
from
3b7ab60 to
be672ca
Compare
mac-kan
changed the title
There was a problem hiding this comment.
Correct me if I am wrong. Currently, it is just a boolean output. Meaning that it can only be linked to one of the diagnostic channels of the EL2044.
The EL2044 has
IF this is meant to only be linked to the open load diagnostics, I would change the variable name to that. If it is meant to be linked to more inputs, then we need to do something about that in the code.
@AlSallami7 is open load enough?
|
To ensure safe operation, I recommend linking the inputs for open load, overcurrent, and short circuit. |
|
Hi I have decided to go for one variable to link to the status word and then we will compare that with masks to see if any of those errors are present. |
|
@federrg I think that is a good decision. I'll fix that asap. |
|
@federrg Follow up: |
Adds an input word to facilitate mapping diagnostics from e.g. an EL2044 terminal to monitor if the output fails. Adds status variables for brake diagnostics.
Masks the brake terminal diagnostics word and maps to two AxisStatus variables.
Adds the diagnostic input signal to the external brake code to prevent unwanted motion when the diagnostic input fails. Since the input variable defaults to TRUE, it is still possible to use the external brake functionality without connecting the diagnostic input variable to any I/O.
mac-kan
force-pushed
the
MBP-330-Brake-With-Diagnostic-Function
branch
from
be672ca to
bd7636f
Compare
@mac-kan I do not think we need 4 words. Just one word per ST_Axis for the brake is enough. To be honest I would have just one status called something like bBrakeError and link all the status as or to them. For troubleshooting then we can go into the status word. |
3 participants
No description provided.